Translation block invalidation prehints in emulation of a target system on a host system

ABSTRACT

Emulation systems and method involving invalidating blocks of translated code in emulation of a target system on a host system in are disclosed. One or more blocks of target system code are translated by the host system to produce one or more corresponding blocks of translated code. The host system uses one or more native target system instructions as hints to invalidate or potentially invalidate one or more blocks of translated code. Blocks containing such hints cause the host system to mark some or all of the one or more blocks of translated code as potentially invalid. The potentially invalid blocks may be re-translated immediately. Alternatively, the potentially invalid blocks may be checked to see if the code in these blocks has been modified. If the code has been modified, corresponding blocks of target code may be re-translated.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of priority of U.S. provisional application No. 60/746,267, to Stewart Sargaison et al, entitled TRANSLATION BLOCK INVALIDATION PREHINTS IN EMULATION OF A TARGET SYSTEM ON A HOST SYSTEM, filed May 3, 2006, the entire disclosures of which are incorporated herein by reference. This application claims the benefit of priority of U.S. provisional application No. 60/746,268, to Stewart Sargaison et al, entitled REGISTER MAPPING IN EMULATION A TARGET SYSTEM ON A HOST SYSTEM, filed May 3, 2006, the entire disclosures of which are incorporated herein by reference. This application claims the benefit of priority of U.S. provisional application No. 60/746,273 METHOD AND APPARATUS FOR RESOLVING CLOCK MANAGEMENT ISSUES IN EMULATION INVOLVING BOTH INTERPRETED AND TRANSLATED CODE, filed May 3, 2006, the entire disclosures of which are incorporated herein by reference. This application claims the benefit of priority of U.S. provisional application No. 60/797,762, to Victor Suba, entitled STALL PREDICTION THREAD MANAGEMENT, filed May 3, 2006, the entire disclosures of which are incorporated herein by reference. This application claims the benefit of priority of U.S. provisional application No. 60/797,435, to Stewart Sargaison et al, entitled DMA AND GRAPHICS INTERFACE EMULATION, filed May 3, 2006, the entire disclosures of which are incorporated herein by reference. This application also claims the benefit of priority of U.S. provisional application No. 60/797,761, to Stewart Sargaison et al, entitled CODE TRANSLATION AND PIPELINE OPTIMIZATION, filed May 3, 2006, the entire disclosures of which are incorporated herein by reference.

This application claims the benefit of priority of U.S. patent application Ser. No. 11/700,448, filed Jan. 30, 2007, which claims the benefit of priority of U.S. provisional patent application No. 60/763,568 filed Jan. 30, 2006. The entire disclosures of application Ser. Nos. 11/700,448 and 60/763,568 are incorporated herein by reference.

This application is related to commonly-assigned, co-pending application No. Ser. No. ______, to Stewart Sargaison et al, entitled REGISTER MAPPING IN EMULATION A TARGET SYSTEM ON A HOST SYSTEM (Attorney Docket No.: SCEA05054US01), filed the same day as the present application, the entire disclosures of which are incorporated herein by reference. This application is related to commonly-assigned, co-pending application Ser. No. ______, to Stewart Sargaison et al, entitled METHOD AND APPARATUS FOR RESOLVING CLOCK MANAGEMENT ISSUES IN EMULATION INVOLVING BOTH INTERPRETED AND TRANSLATED CODE (Attorney Docket No.: SCEA05055US01), filed the same day as the present application, the entire disclosures of which are incorporated herein by reference.

FIELD OF THE INVENTION

Embodiments of this invention relate to emulation of a target computer platform on a host computer platform and more particularly to invalidation of blocks of translated code in emulation of the target platform.

BACKGROUND OF THE INVENTION

The process of emulating the functionality of a first computer platform (the “target system”) on a second computer platform (the “host system”) so that the host system can execute programs designed for the target system is known as “emulation.” Emulation has commonly been achieved by creating software that converts program instructions designed for the target platform (target code instructions) into the native-language of a host platform (host instructions), thus achieving compatibility. More recently, emulation has also been realized through the creation of “virtual machines,” in which the target platform's physical architecture—the design of the hardware itself—is replicated via a virtual model in software.

Two main types of emulation strategies currently are available in the emulation field. The first strategy is known as “interpretation”, in which each target code instruction is decoded in turn as it is addressed, causing a small sequence of host instructions then to be executed that are semantically equivalent to the target code instruction. The main component of such an emulator is typically a software interpreter that converts each instruction of any program in the target machine language into a set of instructions in the host machine language, where the host machine language is the code language of the host computer on which the emulator is being used. In some instances, interpreters have been implemented in computer hardware or firmware, thereby enabling relatively fast execution of the emulated programs.

The other main emulation strategy is known as “translation”, in which the target instructions are analyzed and decoded. This is also referred to as “recompilation” or “cross-compilation”. It is well known that the execution speed of computer programs is often dramatically reduced by interpreters. It is not uncommon for a computer program to run ten to twenty times slower when it is executed via emulation than when the equivalent program is recompiled into target machine code and the target code version is executed. Due to the well known slowness of software emulation by interpretation, a number of products have successfully improved on the speed of executing source applications by translating portions of the target program at run time into host machine code, and then executing the recompiled program portions. While the translation process may take, e.g., 50 to 100 machine or clock cycles per instruction of the target code, the greater speed of the resulting host machine code is, on average, enough to improve the overall speed of execution of most source applications.

Emulation of the target platform by translation relies on blocks of translated instructions. As long as the emulated target platform memory including the original target platform code is unchanged, the target platform emulation can execute the corresponding translated instructions safely. However, certain sections of target code may be modified during normal operation of the target platform. As a result, a corresponding area of the target system memory is changed when the code is modified during operation. To emulate this, the host system may respond to a change in an area of memory by invalidating the corresponding translated target platform instructions. The potentially modified target platform instructions must then be retranslated. However, not all of the code in memory may have been changed and retranslating whole sections of previously translated code when only a few blocks are invalid can take up extra time and processor resources.

Thus, there is a need in the art, for a method and system for translation block invalidation that overcomes the above disadvantage.

SUMMARY OF THE INVENTION

The disadvantages associated with the prior art are overcome by embodiments of the present invention directed to invalidating blocks of translated code in emulation of a target system on a host system in which one or more components of the target system are emulated by translation of target system code. One or more blocks of target system code are translated by the host system to produce one or more corresponding blocks of translated code. The host system uses one or more native target system instructions as hints to invalidate or potentially invalidate one or more blocks of translated code. Blocks containing such hints cause the host system to mark some or all of the one or more blocks of translated code as potentially invalid. The potentially invalid blocks may be re-translated immediately. Alternatively, the potentially invalid blocks may be checked to see if the code in these blocks has been modified. If the code has been modified, corresponding blocks of target code may be re-translated.

BRIEF DESCRIPTION OF THE DRAWINGS

The teachings of the present invention can be readily understood by considering the following detailed description in conjunction with the accompanying drawings, in which:

FIG. 1A is a block diagram illustrating an emulation software that uses translation block invalidation pre-hints according to an embodiment of the present invention.

FIG. 1B is a flow diagram illustrating an emulation method that uses translation block invalidation pre-hints according to an embodiment of the present invention.

FIG. 1C is a block diagram illustrating the handling of chained instructions using translation block invalidation pre-hints according to an embodiment of the present invention.

FIG. 2A is a block diagram of a target device that is to be emulated according to an embodiment of the present invention.

FIG. 2B is a block diagram of an emotion engine of the target device of FIG. 1A.

FIG. 3 is a schematic diagram of a host device that emulates the target device of FIGS. 2A-2B.

DESCRIPTION OF THE SPECIFIC EMBODIMENTS

Although the following detailed description contains many specific details for the purposes of illustration, anyone of ordinary skill in the art will appreciate that many variations and alterations to the following details are within the scope of the invention. Accordingly, the exemplary embodiments of the invention described below are set forth without any loss of generality to, and without imposing limitations upon, the claimed invention.

In embodiments of the invention certain native EE instructions can be used as hints to invalidate or potentially invalidate one or more blocks of instructions and initiate a new translation. In response to these instructions, such as an EE cache invalidate instruction, the EE emulation marks all or some of the translated blocks of code as invalid and begins retranslation.

Embodiments of the present invention may be generally understood by reference to the software block diagram of FIG. 1A and the flow diagram of FIG. 1B. According to an embodiment of the invention, an emulation program 10 may include a translator 12 and a block handler 14. The translator 12 and the block handler 14 may be implemented as subroutines within the larger emulation program 10. The emulation program 10 is executed by one or more processors on a host system. The host system receives program instructions 11 encoded in a form suitable for execution by a target system. The program instructions 11 may be divided into blocks 13, 13′. The translator 12 translates the target system code blocks 13, 13′ into corresponding blocks of translated code 15, 15′ that are in a form that is executable by the host system. The translated code blocks 15, 15′ are stored temporarily in a cache 17 on the host system. The block handler 14 runs the cached translated code blocks 15, 15′, if any are available. If there are no translated code blocks in the cache 17, the block handler 14 calls on the translator 12 to perform a translation of blocks of target system code 11 as indicated by the dashed arrow.

Embodiments of the present invention make use of certain native instructions in the target system code 11 as pre-hints to whether a given block 13, 13′ of target system code 11 is no longer valid as a result of a modification of the underlying target system code 11. For example, in normal operation the target system may generate a cache invalidation instruction when a block 13′ of target system code has been modified during execution of the target system program 11. The cache invalidation instruction provides a pre-hint 19 that the target system block 13′ may have been modified since it was translated and is therefore no longer valid. Other types of instructions that may be used as pre-hints include direct memory access from other processors or local memory in the target system, external events, such as external modification of random access memory (RAM) and software patches. When an invalidation pre-hint instruction 19 is detected in a target system code block 13′ the translator 12 inserts an event check instruction into the corresponding block of translated code 15′. The translator 12 may also generate a hash or checksum 16 for the target system code block 13′ upon translation.

The event check instruction may take the form of a call to a handler 18 to perform a validation and checksum compare 20 on the target system code block 13′ containing the pre-hint instruction 19.

The checksum compare routine 20 accounts for the situation in which a block 13′ contains a pre-hint instruction yet is still valid. The checksum routine 20 compares the hash or checksum 16 generated upon translation with a current checksum for the target system code block 13′. If the two hashes/checksums are the same, the translated block 15′ has not been modified and the translated block 15′ is a valid block 26. Otherwise, the target system code block 13′ has been modified and is an invalid block 31. Valid translated blocks 26 may be executed at 28 by the block handler 14. Invalid translated blocks 31 or groups of blocks that are linked to an invalid block may be deleted at 33 and the memory space for that block may be overwritten. Overwriting the memory space may include marking the memory space as available for overwriting and subsequently overwriting the space with a new block of translated code 17. The block handler 14 then requests a new translation of modified target system code block 13′.

The translator 12, block handler 14 and checksum compare routine 20 may be configured to check and/or re-translate the invalidated or potentially invalidated blocks of translated code in any suitable order. By way of example, the blocks 15, 15′ may be checked, validated and/or re-translated in most recently used (MRU) order.

If only some translated blocks 15, 15′ are potentially invalidated (e.g., because they contain pre-hints 19), the valid blocks 15 may be executed until a potentially invalid block 15′. The checksum compare routine 20 may then check whether the potentially invalid block 15′ is invalid. Alternatively, the potentially invalid block 15′ may be re-translated without checking. If all of the blocks 15, 15′ of translated code 17 are potentially invalidated, execution of the translated code in the cache 17 may be halted and the full resources of a host system processor may be devoted to verification and/or retranslation of the target system code underlying translated blocks 15, 15′.

In embodiments of the invention, the block hander 14 may generate a pointer table 24 that maps program counter values 22 for blocks of target system code to corresponding blocks of translated code. When translated blocks 15′ are invalidated, one or more pointers in the pointer table 24 may be set to point to memory locations for one or more blocks corresponding to host system code for the block handler 14. To re-translate the target system code 11, the pointer table 24 is invalidated and then rebuilt so that the pointers in the pointer table 24 point to blocks of target system code that haven't been modified. With the pointer table 24 rebuilt in this manner, the translator 12 translates blocks of code 11 that haven't been modified.

An emulation method 30 that may be implemented by the software 10 may be understood by referring simultaneously to FIG. 1A and the flow diagram of FIG. 1B. Specifically, at 32, the translator 12 translates the blocks 13, 13′ of target system instructions 11 into corresponding blocks 15, 15′ of host-system code 17. Execution of the translated code 17 may result in a modification of the underlying target system code. At 34 the validator 14 checks the translated blocks 15, 15′ for pre-hints 19 (e.g., cache invalidate instructions). The validator 14 marks blocks 15′ containing these pre-hints as potentially invalid as indicated at 36. At 38 the checksum 16 may be used to determine whether the block 15′ was modified. If it was modified, the block is marked as invalid and re-translated, as indicated at 40. The re-translated block may be check again for pre-hint instructions. If the block 15′ was not modified, it is re-validated, as indicated at 42, and may be executed on the host system, as indicated at 44.

Translations may be chained together so that a function call to the chained translations doesn't always require a pointer table look-up. Once a look-up has been done in the desired chain it can directly branch to the translated function. When a block in such a chain is invalidated the look-up table for this chain must be invalidated. It is also often necessary to keep track of which blocks of translated code are chained to each other and undo that chain. However, such unchaining may be avoided. For example, as shown in FIG. 1C, in some embodiments of the invention, one or more blocks of target system code 11 may be linked together in a chain. For example, target system blocks 0, 1 and 2 may include function calls to block 3. When these blocks are translated, the resulting translated code includes a similar linking of translated code blocks 0, 1, 2, and 3 into a chain 46 such that a look-up in the chain 46 will directly branch to a translated function (indicated as translated block 3). If translated block 3 is invalidated, e.g., because the underlying target system code block 3 has been modified, the target system code is retranslated generating re-translated block 4. The chaining of the translated blocks in the chain 46 would normally have to be undone once the underlying target system code has been re-translated. However, instead of deleting translated block 3 and undoing the chaining, a first instruction 47 in translated block 3 may be replaced with a jump to the handler 18. The handler 18 may then direct the jump to re-translated block 4. Thus, jumps from translated blocks 0, 1, or 2 to translated block 3 are re-directed by the handler to re-translated block 4. The handler 18 may use a link register to determine which translated instruction jumped to translated instruction 3. The term “link register” refers to a special purpose register which holds the address to return to when a function call completes. The handler 18 may determine what emulated target system code instruction should have been running at a point of invalidation, take an exception and re-translate any block of translated code that is linked to that emulated target system code instruction.

By way of example FIG. 2A depicts a block diagram of an example of a target system 100 in the form of a game console device, a Sony Playstation®2. PlayStation is a registered trademark of Sony Computer Entertainment Corporation of Tokyo, Japan. The target system 100 is built around a main processor module 102 referred to as an emotion engine, a Graphic Synthesizer 104, an input/output (I/O) processor (IOP) 106 and a sound processor unit 108. The emotion engine 102 typically includes a CPU core, co-processors and a system clock and has an associated random access memory (RAM) 110. The emotion engine 102 performs animation calculation, traverses a scene and converts it to a two-dimensional image that is sent to the Graphic Synthesizer (GS) 104 for rasterization.

As shown in FIG. 2B, the EE 102 may include a CPU core 122, with an associated floating point unit (FPU) coprocessor 124, first and second vector co-processors 126, 128, a graphics interface controller 130 and an interrupt controller (INTC) 132. The CPU 122, vector co-processors 126, 128, GIF 130 and INTC 132 are coupled to a 128-bit main bus 134. The FPU 124 is directly coupled to the CPU 122. The CPU 122 is coupled to a first vector co-processor (VU0) 126, which is, in turn, coupled to a second vector co-processor (VU1) 128. The second vector co-processor VU1 128 is coupled to a graphics interface (GIF) 130. The EE 102 additional includes a timer 136, a direct memory access controller (DMAC) 138, an image data decompression processor (IPU) 140 a DRAM controller 142 and a sub-bus interface (SIF) 144 that facilitates communication between the EE 102 and the IOP 106.

The CPU core 122 may be a 128-bit processor operating at a 300 megahertz clock frequency using a MIPS instruction set with 64-bit instructions operating as a 2-way superscalar with 128-bit multimedia instructions. These instructions are handled using 128-bit registers 123. The CPU 122 may include a data cache, an instruction cache and an area of on-chip memory sometimes referred to as a scratchpad. The scratchpad serves as a small local memory that is available so that the CPU 122 can perform certain operations while the main bus 134 is busy transferring code and/or data. The first vector unit 126 may be used for animation and physics calculations. The second vector unit 128 may be used for geometry transformations. The GIF 130 serves as the main interface between the EE 102 and the GS 104.

The IOP 106 may include a processor for backwards compatibility with prior versions of the target system 100 and its own associated RAM 112. The IOP 106 handles input and output from external devices such as controllers, USB devices, a hard disc, Ethernet card or modem, and other components of the system such as the sound processor unit 108, a ROM 114 and a CD/DVD unit 116. A target program 118 may be stored on a CD/ROM disc loaded in the CD/DVD unit 116. Instructions from the target program 118 may be stored in EE RAM 108 or IOP RAM 112 and executed by the various processors of the target system 100 in a native machine code that can be read by these processors.

In embodiments of the present invention, target system instructions involving direct memory access (DMA) from the IOP 106 or the scratchpad, may be used as pre-hints for invalidation of translated target system code, as described above.

In embodiments of the present invention, the target system 100 may be emulated using a parallel processing host system 200 so that the host system 200 can run programs written in code native to the target system 100 such as target program 118. FIG. 3 depicts an example of a host system 200 based on a cell processor 201 that may be configured to emulate the target system 100. The cell processor 201 includes a main memory 202, a single power processor element (PPE) 204 and eight synergistic processor elements (SPE) 206. However, the cell processor 201 may be configured with more than one PPE and any number of SPE's. Each SPE 206 includes a synergistic processor unit (SPU) and a local store (LS). The memory 202, PPE 204, and SPEs 206 can communicate with each other and with an I/O device 208 over a ring-type element interconnect bus (EIB) 210. The PPE 204 and SPEs 206 can access the EIB 210 through bus interface units (BIU). The PPE 204 and SPEs 206 can access the main memory 202 over the EIB 210 through memory flow controllers (MFC). The memory 202 may contain an emulation program 209 that implements interpretation and translation of coded instructions written for the target system 100. The emulation program may include features such as those described above with respect to FIGS. 1A, 1B, and 1C. The coded target system instructions may be read from a CD/ROM disc in a CD/DVD reader 211 coupled to the I/O device 208. A CD/ROM disc containing the target program 118 may be loaded into the CD/DVD reader 211. In certain embodiments of the invention, the program 209 may track memory writes by the EE 102, GS 104, DMAC 138 and other processors in the target system 100 to determine whether to invalidate all or only a portion of the translated blocks of instructions.

By way of example, in an embodiment of the invention, a translator 212 running on the PPE 204 may emulate the EE 102 of the target system 100 by translating EE instructions of the target program 118 into machine code 213 that can be run on the PPE 204. In certain embodiments of the invention a dedicated SPE 206 may implement a software interpreter 214 that emulates the IOP 106 by interpreting IOP instructions of the target program 118.

When developing certain pieces of emulated code it may be necessary to invalidate an instruction cache (1-cache) to make sure that it is running coherent code. By way of example, the cache for the EE 102 may be emulated in memory 202. To invalidate an entry in the I-cache appropriately, instructions to overwrite the emulated 1-cache may be trapped. In the case of PS2 emulation, two instructions may be trapped for invalidating—one for the EE 102 and one for VU1 128. Flushing the cache for the EE 102 typically requires retranslation of parts of EE code. The re-translated code has to match the code that is currently in memory 202. Thus, when executing a specific instruction to the 1-cache to invalidate a particular entry it is important to keep track of which instructions straddle which cache translations. The idea is to look for event that requires re-optimization or recompiling of code, read the instruction, translate it to another instruction and change the state of the emulated machine.

While the above is a complete description of the preferred embodiment of the present invention, it is possible to use various alternatives, modifications and equivalents. Therefore, the scope of the present invention should be determined not with reference to the above description but should, instead, be determined with reference to the appended claims, along with their full scope of equivalents. Any feature described herein, whether preferred or not, may be combined with any other feature described herein, whether preferred or not. In the claims that follow, the indefinite article “A”, or “An” refers to a quantity of one or more of the item following the article, except where expressly stated otherwise. The appended claims are not to be interpreted as including means-plus-function limitations, unless such a limitation is explicitly recited in a given claim using the phrase “means for.” 

1. In emulation of a target system on a host system in which one or more components of the target system are emulated by translation of target system code, a method for invalidating blocks of translated code, the method comprising: translating one or more blocks of target system code with the host system to produce one or more corresponding blocks of translated code; using one or more native target system instructions as hints to invalidate or potentially invalidate one or more blocks of translated code; and marking some or all of the one or more blocks of translated code as potentially invalid.
 2. The method of claim 1, further comprising re-translating one or more blocks of target system code corresponding to one or more blocks of translated code that have been marked as potentially invalid.
 3. The method of claim 2, wherein re-translating one or more blocks of target system code includes: invalidating a pointer table containing pointers that map program counter values for blocks of target system code to corresponding blocks of translated code; and then rebuilding the pointer table so that the pointers in the pointer table point to blocks of target system code that haven't been modified.
 4. The method of claim 1, further comprising overwriting one or more memory locations corresponding to one or more blocks of translated code that have been marked as potentially invalid.
 5. The method of claim 1 wherein the one or more native target system instructions include a cache invalidation instruction.
 6. The method of claim 1, further comprising checking with the host system whether the one or more blocks of target system code have been modified.
 7. The method of claim 6, further comprising invalidating and re-translating the one or more blocks of target system code with the host system if the one or more blocks of target system code have been modified.
 8. The method of claim 6 further comprising re-validating the one or more blocks of translated code that have been invalidated or potentially invalidated and executing the one or more re-validated blocks on the host system.
 9. The method of claim 6 wherein checking with the host system whether the one or more blocks of target system code have been modified includes using a hash or checksum to determine whether the one or more blocks of code have actually been modified.
 10. The method of claim 1 further comprising checking and/or re-translating the one or more invalidated or potentially invalidated blocks of translated code in most recently used (MRU) order.
 11. The method of claim 1, further comprising, if only some translated blocks of target system code are potentially invalidated, executing one or more valid blocks of translated code until a potentially invalid block of translated code is reached.
 12. The method of claim 11, further comprising checking whether the potentially invalid block is invalid and/or retranslating the potentially invalid block of translated code.
 13. The method of claim 1, further comprising if all of the one or more blocks of translated target system code are potentially invalidated, halting execution of the translated target system code and devoting full resources of a host system processor to verification and/or retranslation.
 14. The method of claim 1, further comprising generating a table of pointers with the host system, wherein the pointer table maps program counter values for blocks of target system code to corresponding blocks of translated code.
 15. The method of claim 14, further comprising, when translated blocks are invalidated, setting one or more pointers in the pointer table to point to memory locations for one or more blocks of verification and/or retranslation code.
 16. The method of claim 1 wherein translating one or more blocks of target system code includes linking two or more blocks of translated code together to form a chain such that a look-up in a first translated block will directly branch to a second translated block.
 17. The method of claim 16, further comprising if the first translated block is invalidated, overriding a first instruction in the first translated block and jumping to a handler that re-directs the branch to a block of re-translated code.
 18. The method of claim 16, further comprising determining what emulated target system code instruction should have been running at a point of invalidation and taking an exception and re-translating any block of translated code that is linked to the emulated target system code instruction that should have been running at a point of invalidation.
 19. A host system for emulation of a target system, comprising: one or more host system processors; a memory coupled to the one or more host system processors; a set of processor executable instructions embodied in the memory, the processor executable instructions including instructions for implementing a method for invalidating blocks of translated code, the method comprising: translating one or more blocks of target system code with the host system to produce one or more corresponding blocks of translated code; using one or more native target system instructions as hints to invalidate or potentially invalidate one or more blocks of translated code; and marking some or all of the one or more blocks of translated code as invalid.
 20. The system of claim 19 wherein the host system includes a cell processor having a power processor element and a plurality of synergistic processor elements coupled to the power processor element. 